home *** CD-ROM | disk | FTP | other *** search
- From: clamage@Eng.Sun.COM (Steve Clamage)
- Message-ID: <4fiiln$mu4@engnews1.Eng.Sun.COM>
- X-Original-Date: 10 Feb 1996 16:55:19 GMT
- Path: in2.uu.net!bounce-back
- Date: 11 Feb 96 03:20:39 GMT
- Approved: fjh@cs.mu.oz.au
- Newsgroups: comp.std.c++
- Subject: Re: Make type_info name() distinct?
- Organization: Sun Microsystems Inc., Mountain View, CA
- References: <v01530502ad4230963778@[194.163.74.11]>
- X-Newsreader: NN version 6.5.0 #21 (NOV)
- X-Auth: PGPMoose V1.1 PGP comp.std.c++
- iQBFAgUBMR1gn+EDnX0m9pzZAQGybwF/bOdauEQ1nM5g8PrWz8C0zotsiW0bBqj4
- 7JGm4XfHzdvFiwjrGxvRMgRFJGnDXlR2
- =k9lM
-
- dirk@becker.adviser.com (Dirk Becker) writes:
-
- >A better support of persistence was also the intention of my original post.
- >But I did not ask for the additional information in RTTI because I knew
- >already the reason:
-
- >This wide RTTI would allow anybody with a decent disassembler to reverse-
- >engineer your valuable data structures, including full member variable
- >names. This cannot be acceptable for a general-purpose (not only persistence)
- >feature.
-
- Just whose reason was that? So far as I know, no such discussion ever
- took place in the C++ Committee.
-
- No proposal has ever been turned down on the basis of it making code
- easier to reverse-engineer or disassemble. I know of no serious
- discussion within the C++ Committee where such a subject was even raised.
-
- So far as I know, no complete proposal for providing support for
- persistence was ever presented.
-
- The difficulty lies in devising a scheme that is portable, implementable,
- useful, and also acceptable to a wide range of implementors and users.
- --
- Steve Clamage, stephen.clamage@eng.sun.com
- ---
- [ comp.std.c++ is moderated. Submission address: std-c++@ncar.ucar.edu.
- Contact address: std-c++-request@ncar.ucar.edu. Moderation policy:
- http://reality.sgi.com/employees/austern_mti/std-c++/policy.html. ]
-